Changelog for the release of version 1.0.1 #26
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As of this release, I propose to be less detailed about internal changes, as those aren't that relevant to end-users anyway.
jrfnl
force-pushed
the
feature/changelog-1.0.1
branch
from
86a7e96 to
dd15432
Compare
|
Thanks for the super fast update :-D Support odl PHP version we can let in 1.0.1 release. Can you create it? |
|
Released! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of this release, I propose to be less detailed about internal changes, as those aren't that relevant to end-users anyway.
@grogy
As far as I'm concerned, all pertinent technical debt in this repo has now been addressed. The only thing left to do would be to add a code coverage check to the GH Actions run with management via an external service.
In the mean time, I'd like to suggest tagging a new release, so Highlighter can get this version and then can also be made compatible with PHP 5.3 again.
With that in mind, I've pulled this changelog. Happy to do the release if you agree. I've set the release date in this PR (tentatively) at tomorrow.
Re: the version number - this could either be version 1.0.1 or 1.1.0 depending on whether or not "Adding back PHP 5.3 support" is seen as a new feature. What do you think ?